Methods And Systems Using Client-Side Scripts For Review Requests

ABSTRACT

The embodiments of the present system include a review engine that is connected to support modules and databases that receive, store, and retrieve reviews, based upon the subject and the users&#39; relationship to the authors of the reviews. The review engine comprises a social network engine, a rate and rank engine, a credentials engine and a privacy engine. These engines allow reviews to be sorted, filtered and ordered in terms of relevance when presented to the user. Numerous methods are also provided by the system that receive, store and retrieve reviews.

RELATED APPLICATIONS

This patent application is a continuation of U.S. patent application Ser. No. 11/022,282, filed Dec. 23, 2004, entitled, “VENDOR-DRIVEN, SOCIAL-NETWORK ENABLED REVIEW SYSTEM WITH FLEXIBLE SYNDICATION”; U.S. patent application Ser. No. 11/022,567, filed Dec. 23, 2004, entitled, “VENDOR-DRIVEN, SOCIAL-NETWORK ENABLED REVIEW COLLECTION SYSTEM”; and U.S. patent application Ser. No. 11/022,720, filed Dec. 23, 2004, entitled, “VENDOR-DRIVEN, SOCIAL-NETWORK ENABLED REVIEW SYNDICATION SYSTEM,” all of which are incorporated herein by reference.

FIELD OF THE INVENTION

The present invention is related to receiving and storing reviews, and more particularly to fully integrating a social network with a review system to provide trusted reviews based on social network connections.

BACKGROUND OF THE INVENTION

A variety of methods exist today that allow consumers to write reviews of books, products, merchants, restaurants, and other topics. For example, Amazon.com® allows customers to write reviews of products purchased from Amazon®. EBay.com® asks sellers and buyers to review each other, not on the actual product transacted, but on the quality of the transaction itself. Epinions.com®, Shopping.com®, and Bizrate.com® focus on providing reviews of products and merchants to potential consumers, but do so as a shopping portal. Other sites that focus on specific verticals, such as DiamondReview.com™, provide reviews only within the diamond jewelry industry.

For a buying consumer, reviews can be an important part of the purchase decision for a given product or service. However, the state of reviews found on the Internet today is such that many of the reviews cannot be fully trusted. Many reviews are written by sellers (or person's affiliated with sellers) that falsely pose as past buyers, and are therefore biased in favor of the seller. Since it is at best difficult, and usually impossible, to tell the good reviews from the biased reviews, the entire notion of using reviews to make a purchase decision becomes less useful than it could be. Therefore there is no existing system that provides trusted relevant reviews to consumers.

SUMMARY OF THE INVENTION

A system is provided that creates an optimal balance among the interests of vendors, buyers, and review-providers. The system can be used for any type of review, whether it is a review for a product, a service, a person, a work of art, or any other subject for which writing a review might be applicable and desired. The system is socially enabled as it considers each reader's social relationship relative to the author of each review (hereinafter called “user-author”), and considers such relationship when presenting the reviews to the reader (hereinafter called “requesting user”). The system is also designed to allow true user-friendly solicitation of reviews by any merchant or other solicitor of reviews (hereinafter also called “subject-owners”). Furthermore, the system is designed to allow the subject-owners of any review to syndicate or broadcast their reviews through third parties, in a user-friendly and unrestricted fashion, but in a manner that preserves the legitimacy and authenticity of the review. Finally, the system is designed to address concerns about privacy and authenticity relative to user-authors and requesting users.

Embodiments of the present system include a review engine that is connected to support modules and databases that receive, store and retrieve reviews based upon the subject and the requesting users' relationship to the user-authors of the reviews. The review engine comprises a social network engine, a rate and rank engine, a credentials engine and a privacy engine. These engines allow reviews to be sorted, filtered and ordered when presented to the requesting user.

Numerous exemplary methods are also provided that include the reception and delivery of reviews to and from users of the system. The methods of providing reviews include allowing a requesting user to search for reviews within the system and methods of automatically providing reviews based on a requesting user's visit to a website.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of one embodiment of the present review system;

FIG. 2 is a diagram of another embodiment of the review system of the present invention;

FIG. 3 is a diagram of another embodiment of the review system of the present invention;

FIG. 4 is a diagram illustrating exemplary data stored in the review system of one embodiment of the present invention;

FIG. 5 is a diagram illustrating an exemplary social network and social distances that may be employed in the present invention;

FIG. 6 is a flow diagram illustrating an exemplary process of providing reviews in one embodiment of the present invention;

FIG. 7 is a flow diagram illustrating an exemplary process obtaining reviews in one embodiment of the present invention;

FIG. 8 is a diagram illustrating a locator data structure employed in an embodiment of the present invention;

FIG. 9 is a diagram illustrating exemplary information flow within an embodiment of the present review system;

FIG. 10 is another diagram illustrating exemplary information flow within an embodiment of the present review system;

FIG. 11 is an example of data and reviews provided by an embodiment of the review system;

FIG. 12 is a diagram illustrating exemplary information flow within an embodiment of the present review system;

FIG. 13 is an example of data and reviews provided by an embodiment of the review system;

FIG. 14 is a diagram of an exemplary computer network environment that employs embodiments of the review system; and

FIG. 15 is a diagram of an exemplary computer system that enacts and enables the embodiment of the review system.

DETAILED DESCRIPTION OF THE INVENTION

A system is provided that creates an optimal balance among the interests of vendors, buyers, and review-providers. The system can be used for any type of review, whether it is a review for a product, a service, a person, a work of art, or any other subject for which writing a review might be applicable and desired. The system is socially enabled as it considers each requesting user's social relationship relative to the user-author of each review, and considers such relationship when presenting the reviews to the requesting user. The system is also designed to allow true user-friendly solicitation of reviews by any subject-owner. Furthermore, the system is designed to allow the subject-owners of any review to syndicate or broadcast their reviews through third parties, in a user-friendly and unrestricted fashion, but in a manner that preserves the legitimacy and authenticity of the review. Finally, the system is designed to address concerns about privacy and authenticity relative to user-authors and requesting users. The features, methods and structures of the exemplary review system are shown and described with reference to FIGS. 1-15.

FIG. 1 shows an exemplary embodiment of the present system 10 that provides a broad platform for many different types of reviews. Reviews can be written about many different “subjects.” A “subject” can be an online merchant (including a seller on an auction site), an offline merchant, a service (contractors, accountants, lawyers, doctors, classes, seminars, landlords, brokers), a product (movies, books, CDs, software, games, appliances), a person (as a potential romantic date, a potential friend, a potential business partnership, a potential employee, chat buddies, etc.), an employer, a buyer (to assess credit worthiness or other buyer attributes in a qualitative way), etc.

A requesting user interacts with the exemplary review system 10 through the delivery channels 50. The specific details of an exemplary user interface that communicate through the delivery channels 50 are shown in greater detail in FIG. 15. The review system 10 contains a group of support modules 12 that include a subject control panel 14, a locator/verifier/incentive engine 16, a “was this review helpful?” engine 18, a “super reviewer” status engine 20, a category and numerical ranking criteria manager 22 and a social linker user control panel, user signup 24. Connected to the support modules 12 are a subject database 26, a user reviews database 28, and a users and friends database 30. Also connected to the databases are a reviews subset selector module 32, a socially-weighted threaded discussions module 34 and a self-profile module 36 and an anonymous contact module 48. These modules access and augment the data in the various databases to obtain the necessary information required by the engines of the review system 10 as subsequently described.

The system review engine 38 is comprised of a social network engine 40, a rate and rank engine 42, a credentials engine 44, and a privacy engine 46. In one embodiment, the system engine 38 receives and transmits signals to and from the delivery channels 50. The engines 40, 42, 44, 46 can be connected via data busses in a conventional manner, or in any other convenient manner known to those skilled in the art. The signals from the delivery channels include the requesting user's identity (if known) and the subjects and categories of input. The rate and rank engine 42 provides the calculations regarding social distance and final rankings of reviews provided to the requesting user.

A review may be requested through the channels 50. If a review is requested for a given subject, it is first processed by the review subset selector module 32. This module directs the request to the appropriate database and retrieves the subset of reviews relevant to the subject. In addition to the request for a review, the requesting user information is also input into the system. The user ID information goes directly into the review engine 38. The review engine 38 comprised of the social network engine 40, the rate and rank engine 42, the credentials engine 44, and the privacy engine 46 work to provide an ordered list of reviews based on the stored reviews relating to the subject as ordered by a social distance as calculated in the review engine 38. The support modules 12 provide further inputs and information that allow the engine 38 to provide the most pertinent information regarding each user request.

One skilled in the art will understand that one particular configuration of review engine 38 is directed toward hardware modules. Such a one will also understand that equivalent functionality can be implemented by a general purpose computer executing programmed instructions.

A review can also be received and stored in a similar manner. A user may compose a review of a product sold on a website and wish to enter this review into the system (henceforth, the user becomes a user-author). The review would be accepted into the system 10 through the locator/verifier/incentive engine 16. The review is then directed to and stored in the appropriate database. The user-author information is also obtained and stored so a determination and calculation of social distance between a requesting user and the user-author may be obtained. The system 10 employs locator data structures subsequently described in order to process the reviews. In this manner, the system 10 processes reviews based on the subject, the user-author, and the requesting user's relationship to the user-author.

The system 10 can be used to display reviews publicly, a likely scenario for an ecommerce vendor. It can also capture reviews publicly, but not make them available to the public (similar to a typical suggestion box, where members of the public can submit suggestions privately to a merchant). Embodiments of the present system 10 can also be used strictly within an organization, with tightly controlled authorship and viewing rights managed by the privacy engine 46, such as soliciting 360-degree feedback of one employee to another. It can also be used to selectively capture and selectively disclose reviews, such as might be used by an employee to capture all employer references in a way that is validated by a third party (the review-provider), can live forever in time, and can be re-used at will without having to re-contact the provider of the reference. In a similar manner, the present system 10 can be used by applicants to academic programs, such as business or law school, where a reference is typically required. The present invention therefore maps a user's personal social network to products, services, vendors, buyers, sellers, potential business partnerships, and even potential romantic encounters that the user might be contemplating.

FIG. 2 shows an exemplary embodiment of a multi-channel format syndication system used in the review system 10. The system 52 in this example contains a plurality of databases such as a subject database 54, a user reviews database 56, a users (authors of user reviews) database 58, and a users and friends database 60. Connected to these databases is module 62 that selects reviews, sorts and adds privacy features based partially on social distance between a user-author and a requesting user. Also included in the system 52 are modules 64 that applies syndication channel specific filtering of reviews and module 66 that applies syndication channel specific formatting. Module 66 is connected to multiple channels 68 for communication. The types of channel specific filtering and formatting are determined by the type of electronic delivery system employed as subsequently described.

FIG. 3 illustrates an exemplary review submission system 70 that employs a locator as would be used with the review system of FIG. 1. A locator code is submitted by a customer into the system via lookup locator and subject module 72. Module 72 accesses locators database 78 and references subjects database 80 (an exemplary record of database 78 is shown in FIG. 8). In module 74 the review forms are presented based on the locator instructions and the results are stored in user reviews database 82. Module 76 requests that the user-author (formerly just a customer) register or sign in, and then requests that the user-author submit information used to create a social network. Module 76 accesses user database 84 and friends database 86. Using this embodiment, a user-author's profile and social network are entered for further processing within the system 10. The locators used in the present system 10 connect customers to subjects so that an almost instantaneous connection between customers and subjects may be obtained in order to provide review forms to a customer. The features and methods provided by FIGS. 1-3 are described below.

Once a user's social network is provided to the review-provider system 10, the review-provider maps that user's social network to other users' social networks, creating a tree-like structure, each node of the tree representing a user, and every connection of nodes representing a degree of separation. The “social distance” between any two users is equal to the shortest path between the two users in such a tree.

An additional overlay to the social network is to request each user to describe the relationship with each “friend” submitted to the network. For example, if the user describes person A as a “spouse” and person B as a “co-worker,” there is a clear hierarchy of trust despite an otherwise equal “social distance.” Furthermore, such relationships can enable otherwise impossible privacy options that allow the user-authors to share reviews with requesting users that are multiple degrees of separation away, yet not breach the user-author's actual identity (as subsequently described).

The present embodiments of the system 10 map the concept of a social network into the notion of reviews. The system 10 offers reviews by friends, by friends of friends (2 degrees of separation), by friends of friends of friends (3 degrees of separation), and so on, in addition to any reviews offered by recognized experts and by strangers. Whenever reviews are presented to a requesting user via the review engine 38, the reviews can be sorted based on the “social distance” between the user-author and the requesting user. The “social distance,” as previously described, is the number of degrees of separation between the user-author and the requesting user, based on the requesting user's and/or the user-author's social networks.

A social network can be implemented in the system 10 as described above with two data structures 88 as shown in FIG. 4. The data structures 88 can be implemented as a memory array, as an SQL table, or any other practical method. The first data structure consists of a user table 90, which contains a unique userID number 94 for each user of the review-provider system, as well as any additional information 96, such as name, email address, or any other appropriate and relevant registration information. The second data structure consists of a friends table 92, which contains pairs of userID numbers 98 and friend-userID numbers 100, and any other relevant information 102 such as relationship, names, etc. Each pair of userID numbers 98 and 100 consists of two users who have established a link as a “friend” in the social network. Therefore, if a pair consists of (1,2), representing userID #1 and userID #2, this represents 1 degree of separation between userID #1 and userID #2.

A social network can be formed from any number of unique or nearly-unique identifiers to users, such as phone numbers, social security numbers, or email addresses. Some of these identifiers can be used in combination, or in combination with secondary identifiers such as name and address. When the user registers to the review-provider system 10 (as in FIG. 3), the user is given the opportunity to submit their social network, in the form of a list of unique or nearly-unique identifiers to other users whom the user considers to be a friend. This is accomplished by asking the user to manually enter information such as email addresses, or can be automated by retrieving a user's contact information from any number of existing repositories such as the contact list on the user's email/contact software (such as Microsoft Outlook® or Palm Desktop™), online email provider (such as Yahoo Mail), other device (such as a cellular phone or PDA containing such information), or provided in metadata format such as FOAF (http://www.foaf-project.org).

A social network can be augmented by capturing the relationship between users and groups of users. For example, if a user works at a particular company, she will have a slightly higher amount of trust for a co-worker than she would a complete stranger. This is true even if there is no formal social connection between her friends and the co-worker's friends (i.e. “infinite” degrees of separation). The same assertion can be made for users who study at the same university or school, are members of the same alumni network, go to the same church, attend the same social events, pursue the same hobbies, are members of the same professional or leisure club, etc. The invention allows users to add groups of people as friends in the social network. The group of people is identified in aggregate as a single company, university, or any other appropriate identifier.

Multiple pairs 98 and 100 are combined in a tree-like structure to establish a given user's social network, as shown in FIG. 5 for the sample data set shown in FIG. 4. FIG. 5 shows an exemplary tree-like data structure 104, along with the sample social distances 106, as shown in the tree 104. In this example user 1 is friends with users 2 and 3. User 2 has friends 4, 15, 19 and 5. User 4 has friend 27, while user 5 has friend 23. User 8 is friends with 23 and 25. The social distances 106 refer to the number of connecting lines between users. For example, to connect user 15 to 23, three connecting lines must be made, therefore the social distance is three.

Using the exemplary social network information as above, whenever a requesting user requests reviews for a given subject, the computer review system 10 executes an exemplary process as shown in FIG. 6. After starting, the process enacts step 110 where a requesting user requests reviews for a given subject. All reviews pertaining to the given subject (excepting those that may be filtered as disclosed later) are selected in step 112. In step 114 it is determined if the requesting user is known and signed in. If the requesting user is registered and signed in, the requesting user's userID becomes available to the review-provider as part of the query, either through a cookie or any other means, and the “social distance” of each selected review's user-author is calculated in step 116 with respect to the requesting user. The reviews are displayed in sorted order and can use privacy settings that include “social distance” in step 118. If the requesting user's userID cannot be determined, step 120 is enacted where the reviews are displayed in sorted order and can use privacy settings that do not include “social distance.” It is noted that for other embodiments of this process 108, particularly with regard to the sequence (for example, the retrieval and reviews and the computation of “social distance” can occur nearly simultaneously), there are many ways that the “social distance” can be used to influence the sort order and/or the privacy settings of the reviews.

Another feature and embodiment of the invention is the connection of threaded discussions to the reviews (also known as “message forums”). Module 34 in FIG. 1 includes messages or entire threads of messages in the system 10, so when the requesting user requests a review on a subject, the likelihood that the requesting user will find a friend who has commented on the subject will increase. When this happens, an entire message thread (as subsequently described) can be considered to be of the same “social distance” as the user-author of the message within the thread (as subsequently described) with the smallest “social distance” to the requesting user, thus bringing additional trusted information to the requesting user.

It is possible to tightly integrate a message forum 34 to the review system 10. In such an implementation, the initial review would serve as the initial message in a “thread” of messages. Multiple users would be able to post and reply to the thread, thereby adding many messages and comments to the initial review. The subject-owner about whom the review is written would, in some cases, be able to control whether an integrated message forum is permitted for their reviews, and which users may post on such a forum (e.g., only the subject-owner, only the subject-owner plus user-author of the review, only registered users, everyone at large, etc.). A “social distance” can be computed between the user-author of each message in the thread and the requesting user, and the reviews and comments can be provided in sorted order based partly on the “social distance.”

Embodiments of the present invention therefore provide a search function where the documents (e.g., web pages, PDF files, etc.) would be sorted by relevance based on keywords (well known in the art), other metrics (such as Google's PageRank method), as well as by the “social distance” between the authors or other endorsers of said documents and the user performing the search. This significantly increases the value of the documents retrieved, since the trust level of the source of the documents would be higher.

For example, if a requesting user searches for “books” and the review search engine 38 finds 25 book providers (e.g. subjects who provide books), the results would be sorted based on a metric at least partially related to the “social distance” of the reviews that are written for each of the 25 book providers. Therefore, if a close friend of the requesting user had recently experienced a given book provider and written a review, that book provider would be listed first, and the requesting user would be able to read his or her close friend's review on that book provider as part of the search result.

An additional feature of this invention is the overlay of a category search within the system 10. For example, if a requesting user is looking for “Chinese Restaurants in Mountain View, Calif.,” the results would be retrieved and sorted based on a metric at least partially based on the “social distance” of the user-authors of the reviews written for each of the restaurants that fit the category criteria.

An additional implementation and embodiment of the invention is an overlay for RSS feeds and blogs, where the links would be sorted based partly on the “social distance.”

One of the most formidable challenges in collecting reviews is the mere act of motivating customers and system users to write reviews. The most opportune moment for a customer to write a review is within a few days after the sale is completed, the product is first used, or the occurrence of some other substantial experience with the subject that empowers the customer to write a review. Depending on the nature of the product or service and how it was purchased, many different collection methods are appropriate.

An exemplary method 122 of collecting reviews is shown in FIG. 7. After starting, step 124 is enabled where the subject-owner first requests that the review-provider create a finite set of locator codes, each containing a unique locator code comprising of a set of alphanumeric characters, and perhaps partially describing a future transaction (the minimum description would simply include the identity of the subject). Upon request in step 126, the review-provider generates the locator codes by creating random but unique alphanumeric sequences, creates a database record, and delivers the locator codes to the subject-owner, in either print form or in electronic form. The print form is useful for brick and mortar merchants, whereas the electronic form is useful for online merchants, but the two are interchangeable. The system and review-provider allow the subject-owner to amend the locator record only between the period of time that a given locator code is created and when it is used or expended by a customer in step 128. This allows the subject-owner to add transaction information to the locator record upon issuing the locator code to a customer in step 130.

Once a customer obtains a locator code from the subject-owner, the customer goes to the review-provider website and types in the locator code in step 132. Optionally, the subject-owner can deliver the locator code electronically, such as contained within a URL. Assuming that the locator code is contained in the review-provider's database, the locator code causes the database to retrieve the identity of the subject, any transaction-level information including the customer's name, and any additional instructions in step 134. Based on the information retrieved, the customer is presented with forms that allow the authoring of a review in step 136. Using the additional instructions, it is possible to ask the customer to write additional reviews on specific aspects of the transaction, to ask the customer to register to become a registered user of the review-provider system, to ask the customer to create a social network within the review-provider system, to grant coupons or other incentives to the customer as a reward for completing a review or other tasks as specified in the instructions, and any other instruction. The fields in the locator record containing the transaction-level information and the additional instructions can be implemented in many ways, but a convenient way is to use XML or any other data format that can store metadata.

FIG. 8 shows an exemplary locator record 138 that would be used in the present system as shown in FIG. 3. The locator record contains a locator code 140, a subject ID 142 corresponding to a subject, an identifier 144, and additional instructions 146. Additional locator codes 148 are also stored that may reference additional subjects or locator records for example. Each locator code within the locator database 78 allows quick access to the appropriate databases stored within the system 10. This allows for real-time processing of information by the system 10 and reviews to be accepted from and provided to the customer.

One variation of the method of FIG. 7 would be for brick and mortar subject-owners who perform most of their transactions without the use of the Internet, to create paper cards, each card containing a unique locator code (printed by the review-provider or the subject-owner) and issue such cards to each customer with every purchase or transaction. The card could contain simple instructions for the customer to visit the review-provider's website and submit the locator code. After the customer submits the locator code, she would be presented with the electronic forms necessary to complete the requested review. Under this basic system, it would not be possible to include transaction-level information such as the customer's name or what the customer purchased, unless the customer submitted that information as part of the review.

Another embodiment of the above system and methods would be to include the locator code on the cash register receipt of every purchase. While this requires tighter initial integration between the subject-owner's point of sale system and the review-provider, once the integration work is complete the system becomes truly seamless for the subject-owner, and the inclusion of transaction-level information and customized additional instructions into the locator record can optionally be automated.

Another exemplary use of the above embodiments that is possible for brick and mortar subject-owners would be for the subject-owner to transmit names, email addresses, and any other transaction-level information to the review-provider on a regular basis (such as hourly or daily) of all transactions completed during the period. The review-provider would then generate a locator code, combine the locator code with the transaction information provided by the subject-owner, and generate and send an email directly to the customer, requesting a review, and containing the unique locator code.

An online subject-owner could use the embodiments of the invention to transmit the locator code electronically to customers, such as sending an e-mail message to customers containing a unique URL which contains a hyperlink to the review-provider website and the locator code. After the customer clicks on the hyperlink, they would be redirected to the review-provider website and presented with the electronic forms necessary to complete the requested review.

Another exemplary use of the method of FIG. 7, appropriate for transactions completed entirely online, would be for the subject-owner to direct the customer's browser to the review-provider's website at the conclusion of a purchase. Part of the redirection would pass transaction-level information to the review-provider. The review-provider would then request the review from the customer, without the need for a locator code at all.

Another example of the present system that would be appropriate for manufacturers of products is to include a card with a locator code inside the actual product, perhaps along with the warranty/registration procedure (or perhaps even as part of such a procedure, which might be triggered as part of submitting the locator, as an additional instruction as described previously). In this variant, the inclusion of the card containing the locator code would be at the point of manufacturing the product, not necessarily at the point of sale.

The various exemplary methods presented here offer several advantages that become critical to increasing the likelihood that the customer will complete the review process. First, it minimizes data entry and lookups that need to be performed by the customer. All the customer must do is visit a website, type in a locator code, and then follow the prompts. Second, because the nature of the transaction and subject are known (due to entry of the locator code), only relevant questions are asked of the reviewer. Third, at the end of the review, the subject-owner can optionally offer a reward to the customer for completing the review. Fourth, because many subject-owners would use this exact method and only the locator codes would vary, this would become a familiar usage pattern for customers, thereby reducing first-time anxiety in using the system.

Aside from increasing the likelihood of completing the review, this process also offers the advantage that customers who submit reviews are already pre-validated as a customer who has made a bona-fide purchase from that subject-owner. This eliminates the possibility of a fraudulent or false review, thereby increasing the overall faith that users will place in the system 10. This feature can be strengthened by having the subject-owner submit to the review-provider the name or other identifier of the customer to whom it issued a specific locator code, before that customer writes the review, as part of the transaction-level information in a given locator record. When that customer writes the review, the review-provider can then verify that the customer's name matches the name that was provided (and explicitly authorized) by the subject-owner to write the review. Matching can be done within the system 10 using any number of “fuzzy logic” techniques that match a customer's name or other non-precise identifiers, including multiple such identifiers (an example of a non-precise identifier is a customer's name; whereas examples of a precise identifier are their social security number or their email address).

The present embodiments therefore allow the capability to add transaction-level information to a given locator record. The subject-owner can specify the name, email address, telephone number, or any other identity information of the customer and is therefore authorized to complete the reviews and additional instructions. If a customer matching the name as submitted by the subject-owner completes the task, the reviews can be marked as “verified” by the review-provider system 10, and this can be communicated to any requesting user. The name can be matched using a soundex function (or similar fuzzy logic), and the subject-owner can “appeal” an incorrect matching, which will then be approved or disapproved manually by the staff of the review-provider.

The capability to add additional instructions to a given locator record is also a feature of the present system 10. For example, if a customer buys a digital camera from a given online vendor, the single locator code can trigger one review for the digital camera itself, another separate review for the online vendor, and yet a third review for the customer service representative who assisted with the purchase of the camera. Another instruction would be to request that the customer register to become a registered user of the review-provider, and then to create a representation of that customer's social network. In the absence of additional instructions provided by the subject-owner, the review-provider may provide default additional instructions.

A locator record as shown in FIG. 8 can have an expiration date, after which time the locator code cannot be used (if it has not been used already). The subject-owner can cause the review-provider to generate a set of locator-codes using the review-provider's website as an ordering kiosk.

The review-provider system 10 can meter the generation of locator codes, and can either limit the number of locator codes that can be generated within a specific period of time or for a specific subject, and/or can charge money for the generation of locator codes.

In the absence of a locator code, it is still possible for the system 10 to collect reviews that a user wishes to contribute. These reviews could be marked as “unverified” or some other such appropriate symbol, meaning that they were not solicited by the subject-owner and were contributed entirely voluntarily. This is the status quo in most review-providers today, and invites fraudulent negative reviews by competing subject-owners, as well as fraudulent positive reviews written by the subject-owners about themselves. To make this system 10 somewhat more resistant to this type of attack, a credit card authorization can be optionally used, wherein the user verifies his or her identity but does not incur an actual charge to the credit card (described later).

If, during the process that a user submits a review, the user fails to complete the registration or sign-in process, the review is still retained and used, but anonymously. Furthermore, a persistent cookie is placed in that user's browser with a unique identifier to that review. If the user ever visits the review-provider's website again and does sign in or register, any and all reviews that are anonymous but that were authored from that browser (and assuming the cookie is still in place) are automatically assigned to that user as the user-author.

Once reviews have been written, it is desirable to be able to retrieve the reviews in several different ways, within one centralized area, usually the review-provider's website. The “search box” metaphor is used, except the search box is overloaded with additional retrieval-oriented functionality that is invoked when the requesting user formats the query in specific ways.

Various types of uses and interfaces are therefore provided by the present invention. The interfaces would be generally provided by a display 230 as detailed in FIG. 15. The interface may include a “search box” to allow a requesting user to interact with the system 10. Referring to the method of FIG. 6, if a requesting user types the word “diamonds,” the system would return subjects that either contain the word “diamonds” or are perhaps related in some way.

Another way to use a search box is for the requesting user to submit a unique identifier to the subject. There are a number of unique identifiers available to merchants and service providers: Web site URL and phone number (with area code). For products, the UPC code is the best available unique identifier (which may be automated by scanning the UPC). For individuals, the social-security number is one good unique identifier, as is an email address. Furthermore, the review-provider can assign unique identifiers to subjects, including numbers or keywords. It should be apparent to those skilled in the art that there are many unique identifiers available to subjects such as products, merchants, and individuals. Whenever a unique identifier is submitted, the system automatically retrieves reviews for that given subject.

Another embodiment of the system 10 regarding the use of a search box is to submit a location. This can be done manually (type in an address or latitude/longitude), or can be done automatically with the assistance of a GPS receiver. If the location submitted matches with a subject, the review information is returned by the system. Location can be matched by address, or by coordinates. In the case of coordinates, the submitted coordinates would be compared against each subject's coordinates along with a bounding function that describes all other possible coordinates that fall within the subject's physical location (or nearby), and if a match is made, the review information is returned by the system.

A further exemplary way to use the search box is for the requesting user to submit a locator code. When a locator code is submitted, the system automatically recognizes the entry as a locator code, and proceeds to collect the review from the requesting user following the instructions in the locator record corresponding to the submitted locator code. In addition to providing reviews, the system 10 aggregates certain functions and information that significantly enhance the value of the reviews.

Referring again to FIG. 1, a variation of the embodiment of the system 10 is the addition of editorial reviews (apart and separate from user reviews). By definition “editorial” reviews are provided by recognized experts in the given field (those skilled in the art will recognize that an “expert” is a special type of user-author). An editorial review function allows the subject-owner to individually request any known expert to submit a review. This is accomplished by issuing a locator code to the expert. After the expert writes the review, the subject-owner can move the review to a special area reserved for “editorial reviews.” The identity of the expert who writes such a review is disclosed to the extent that the expert permits, just as in normal reviews; however, because the subject-owner requested the review from that expert, the subject-owner may also request that the expert allow full identity disclosure for that particular review. Any requesting user who reads that review will assign trust commensurate with the fame and credentials of the given expert.

Another value-added function is the addition of credentials and certifications issued by third parties that is provided by the credentials engine 44. For example, TRUSTe® (http://www.truste.org) offers certification of privacy practices; likewise, the Better Business Bureau® (http://www.bbbonline.org) offers certification pertaining to ethical business practices. There are also other third-party certification agencies that pertain to specific domains; for example, the Jewelers Board of Trade™ (http://www.jewelersboard.com) that assigns credit ratings within the jewelry industry. The system 10 can therefore also provide these certifications with the review information.

The rate and rank engine 42 provides the function of assigning an overall rating number to each subject. This would allow requesting users to quickly rank the subjects in a given category, if such a ranking were desired. The overall rating number is computed individually for each requesting user, using metrics that include the “social distance” (as already disclosed) between the requesting user and the aggregate of all user-authors that have written reviews applicable to that subject. Other metrics that may be used in conjunction with the “social distance” include the rating assigned by each user-author, how/whether the user-author has been identity-authenticated, and how/whether the user-author was pre-authorized by the subject-owner (by issuing a locator code).

The support modules 12 add further features to the system 10 by adding questions and rating criteria for reviews that are known to fall within known categories. For example, if a user is asked to write a review for a diamond jeweler, appropriate questions and rating criteria that would augment the value of the review include selection of rings, appropriate lighting in the showroom, convenient store hours, and other domain-specific questions and criteria. The system 10 includes a capability that allows subjects to be categorized; as such, when a user writes a review or submits a locator code, the category is retrieved along with the subject's other information, and based on the category, additional questions and rating criteria are retrieved and presented to the user, for example in the review authoring form. An extension of this capability allows individual subject-owners to augment and add questions and rating criteria to their own review authoring form, above and beyond any augmentation that might occur based on the category.

The present embodiments therefore offer and facilitate a high degree of aesthetic (or other) customization by the subject-owner to the pages in which their reviews are contained. The review-provider could provide a special version of a site builder to a subject-owner that would allow the creation and building of the pages, by adding components (for example, “drag and drop” components) that are specific to the review-provider. These components include actual reviews, credentials, logos, descriptions, directions, and similar. It is important to emphasize that the tool would only allow the subject-owner to control the placement and aesthetics of reviews and credentials, not actually modify the content of the reviews or credentials. Other components that would be useful for subject-owners that happen to be merchants include methods for users to make contact with or send a request to the subject-owner; furthermore, these requests could be seamlessly integrated to a CRM (Customer Relationship Management) functionality that could be provided as an additional tool or by a third party CRM vendor.

Once a review has been written about a given merchant, product, or other subject, it is desirable that the review be disseminated as widely as possible. To that end, the present invention includes a flexible syndication system that permits the review to be easily distributed to an unlimited number and variety of different websites, devices, and other media. Furthermore, whenever possible, the presentation of such reviews should be customized to the media, website, or device being used by the requesting user to view the reviews. This means that in addition to a “social distance” metric between the requesting user and each review weighing significantly into the sorting and presentation of the reviews that are chosen to be displayed for the requesting user, the aesthetic presentation of the reviews is customized to the syndication channel, both to the physical affordances offered by the channel (such as a small display in a portable device), as well as the business needs governing the channel (such as the front page of the merchant's own website).

In addition to the numerous examples described above, FIG. 9 also shows an exemplary embodiment of the present invention. In this example, an implementation of a multi-format syndication system 150 involves three separate computing entities as shown in FIG. 9, the user's browser 152, the review-provider's server 154, and the third-party website 156. Steps 1-6 indicate flows of information or actions within this system 150. In FIG. 9, a requesting user with an Internet browser such as Netscape Navigator® or Internet Explorer® visits a 3rd-party website (1, 2). The 3rd party website delivers content as customary (3), but as part of its content it delivers a client-side script (such as JavaScript), frames, or any other command or technique that will initiate contact between the requesting user's browser 152 and 154 the review-provider's server (4). The transmission that occurs in (4) includes, if available from a previously stored persistent or semi-persistent cookie in the requesting user's browser or by other client-side means, the requesting user's unique identity. Furthermore, part of the transmission in (4) includes a request for specific reviews or category of reviews, based on the content that was sent to the browser by the 3rd-party website. The review-provider's server 154 retrieves the reviews from its database, computes a “social distance” between the requesting user and each review's user-author, and then returns the list of reviews, sorted and presented at least in part by the “social distance” (5). The review content is merged with the content at 152 the requesting user's browser (6), and the requesting user perceives that all the content is coming from the 3rd-party website 156. However, the content of the reviews is customized for that requesting user, and shows the most relevant reviews first. If a different requesting user visits the 3rd-party website 156 at the same time, the content served by the review-provider's server 154 will be customized to that different requesting user. Of course, if a requesting user is not known to the review-provider's server, the content is presented in a default manner that does not include any “social distance” metric.

The third-party website 156 might consist of (perhaps competing) review providers, information websites, the subject-owner's own website (such as a merchant), or any other website. This same technique can be accomplished in many different ways than shown above. The third-party website 156 may communicate directly with the service-provider's server, and retrieve information that would then be passed through the third-party website to the requesting user, therefore obviating the need for a connection directly between the requesting user and the review-provider's server (such connection is shown in dashes in FIG. 10 to indicate that it is optional).

FIG. 10 contains another diagram 158 of the possible flow of information that could be used to implement this invention. This system contains the requesting user's browser 160, the review-provider's server 162, and the third-party's website server 164. Furthermore, there are a number of additional transmission and presentation methods such as RSS, web services, frames, client-side scripts, browser toolbars, etc., that should all be considered equivalent and inter-replaceable for purposes of this invention. Furthermore, a review-provider's server 162 is not required if all of the review data is contained in the 3rd-party website server 164. Likewise, a 3rd party website 164 is not required if all of the content and review data is being served by the review-provider's server 162. Lastly, the requesting user browser 160 can be generalized to any client software running on any device capable of being connected to a digital network (such as a cellular phone or PDA).

In one implementation, the requesting user visits the review-provider's website 162 and requests reviews for one specific subject (merchant, product, etc.), for a given category of subjects, for a given location, for a given keyword combination, or any other criteria of similar nature. The reviews that are relevant to the requesting user's request are selected from a database, and the presentation is sorted by a metric that includes “social distance.”

In another implementation, the 3rd-party website 164 is the subject-owner's own website, such as a merchant that wishes to display its reviews to all requesting users that visit the merchant's website 164. It would be feasible and highly desirable to include reviews directly on the “home page” of the merchant's website 164, and to have those reviews sorted and presented at least partially by “social distance.” The net result would be that if requesting user A visits the merchant's website 164, they would automatically be presented with the reviews written by requesting user A's friends, friends of friends, etc., in sorted order by a metric that includes “social distance.”

Another application of the multi-format syndication system is for advertising. Whenever a subject-owner wishes to advertise his or her products and services, part of the advertising could contain the title and author of a small subset of reviews, presented and sorted by a metric that includes “social distance.” Referring back to FIGS. 9-10, the “3rd party website” in this case would be an advertising provider's website 164 such as Yahoo.com™ or About.com®.

The net result is that every advertisement would be directly targeted at the requesting user who is viewing such advertisement, presenting that requesting user's friends' reviews alongside the subject-owner's logo or other promotional message. An example of a promotional message 166 provided by the present system is shown in FIG. 11. In this example, friends Linda Jones and Tom O'Reilly have stored reviews relating to Doe Jewelers, and these reviews have been automatically provided by the system. This promotional message 166 would be displayed on a requesting user's computer screen as described with reference to FIG. 15 for example.

Another exemplary system 168 is shown in FIG. 12. System 168 contains the user's browser 170, the review-provider's server 172, and an advertising website server 174. In system 168 the review-provider 172 also serves the advertisement in this case, there is only communication between the requesting user browser 170 and the review-provider 172 for the advertisement customized for the requesting user as shown in FIG. 12. This has the benefit of avoiding possible network delays. This type of application can be extended to all sorts of advertising where the requesting user's user ID can be made available to the review-provider's server 172, including “pay-per-click” advertising, banner advertisements, classifieds, auctions, etc. The multi-format syndication system 168 can also be used in “offline” applications where the requesting user's User ID can be made available; for example, in television advertisements provided by addressable cable or satellite systems, the advertisement could include a blank area where reviews sorted by a metric that includes “social-distance” can be displayed individually to requesting users.

A slight variant from the advertising system 168 described above is one in which the advertising is replaced by a “compliance seal” provided by the review-provider. As shown in FIG. 13, information 176 provided on a requesting user's browser by the system includes a sample seal 178 and a website link 180. The “seal” 178 can be displayed on any website, but would most likely be displayed on the subject-owner's website. The seal 178 would provide to the requesting user with information about that subject that is stored by the review-provider. Also, the contents of the seal could vary based on the “social distance” between the requesting user and the aggregate of user-authors of reviews that pertain to the given subject and include a message from a friend. This information 176 would be displayed on a requesting user's computer screen as described with reference to FIG. 15 for example.

Another application of the multi-format syndication system as shown in FIG. 2 is for a location-enabled device such as a cellular phone, PDA, or vehicle navigation console. When a requesting user is traveling in a given neighborhood or is physically standing inside a particular store, the location of the requesting user plus the requesting user's id can be used by the review-provider's server to provide location and “social-distance” to specific reviews. In this embodiment, the location-enabled device is represented by the requesting user's browser 152.

Another application and embodiment of the multi-format syndication system 52 is for in-store displays. When a requesting user enters a store, the in-store display senses the requesting user's identity and transmits it to the review-provider's server, which then returns reviews sorted by “social distance.” The in-store display then displays the reviews for the benefit of the requesting user. In this embodiment, the in-store display is represented by the 3rd-party website 156.

Another embodiment and variation of the multi-format syndication system 52 is for displays in general. Examples include billboards and other sorts of smart advertising that automatically tailor the message based on the requesting users who are walking by. In this exemplary embodiment for example, a requesting user may walk through an airport and the advertisements briefly contain pictures and/or messages from his friends, telling the requesting user to shop at certain merchants. The pictures would change based on the requesting users who are walking by (to their friends). The identity of the requesting users would be sensed in any number of ways, including facial recognition, by a location-enabled device being carried by the requesting users that transmits the requesting user's location to a network that is then accessed by the displays, or by a peer-to-peer connection (such as Bluetooth or WiFi) between a requesting user's personal device and the displays. In this embodiment, the displays in general are represented by the 3rd-party website 156 and the device being carried by the requesting user is represented by the requesting user's browser 152.

Another application of the multi-format syndication system is for message forums, instant-messenger buddy lists, dating/singles matching networks, or any other application that enables interaction with other people. The application hosted on the 3rd-party website 164 transmits the requesting user's identity to the review-provider's server 162, which in turn returns “social-distance” enabled review information for the requesting user accessing the third-party website from the requesting user's browser 160. This information is seamlessly integrated into the message forum, buddy list, matching network, or any other such application.

One element that is important to merchants, manufacturers, persons, or any other subject-owner for which a collection of reviews exists, is the ability to “filter” reviews received. The filtering mechanism of the above systems allows the subject-owner to apply filters at least 1) specific to the syndication channel (i.e. reviews that appear on the subject-owner's home page, vs. reviews that appear on advertisements, vs. reviews that appear on the review-provider's website, vs. reviews that appear on third-party website #1, vs. reviews that appear on third-party website #2, etc.), 2) specific to how the review was submitted (i.e. by use of a locator code, vs. completely unsolicited), 3) specific to the user-author of such review (i.e. specific user-author vs. certain standing vs. verified vs. anonymous), 4) specific reviews that the subject-owner chooses to withhold from viewing by the public, and 5) any number of other filters that would be obvious to those skilled in the art. The filtering mechanism would allow the subject-owner of the reviews to withhold publication of given reviews. It would never allow subject-owners to modify the contents of any review. In order to achieve full transparency despite the presence of subject-owner controlled filtering, the review-provider can inform all requesting users of any set of reviews whether or not the filtering option (and which one) is being utilized by the subject-owner. This leaves the choice up to the subject-owner, who must decide to either filter reviews (but readers will know that the subject-owner is filtering) or confirm to requesting users that all reviews are being shown unfiltered (but risk a handful of inevitable negative reviews).

Other features of the present embodiments are the ability to allow subject-owners that have little technical knowledge to 1) easily integrate/deliver reviews from the review-provider to the subject-owner's own websites, advertisements, third-party websites, in-store displays, and even in casual conversation or a casual e-mail, 2) control the filtering of reviews (if they choose to apply filters), 3) control and access all of their billing information, and 4) manage any other issues related to their use of the review-provider system. The review-provider system 10 provides each subject-owner with a private area within the review-provider website from which subject-owners may perform these functions with ease.

Another desirable feature of this system 10 is the ability for the review-provider to meter or limit access to syndicated review information on a per-channel basis. This is desirable because widespread syndication will consume bandwidth and other resources from the review-provider. The system 10 can meter and limit access based on each “hit” or request that is made for the reviews from a given subject, for each “hit” or request that is made for a subset of the reviews as pertaining to serving advertisement or a seal program, for each “hit” or request that is made for portable devices, for displays (in-store or otherwise), or for any other request made to syndicate review information in any way to a third party website 164. The metering information can be used to limit access when the resource allocation is depleted, or to generate billable charges to the subject-owner or to any other third party based on the amount of use of the syndication system.

The success of any review system ultimately depends on the amount of trust that the general public chooses to place upon any such system. In this case, “trust” is the composite of 1) that the general public believes that private information submitted to the review-provider will not be handled, used, or disclosed in any improper way, and 2) that the reviews contained in the review system are largely legitimate, as opposed to being fraudulently written by sellers or their agents, about themselves or about their competition.

One way to prove the legitimacy of reviews of the present embodiments is to disclose the full name of the user-authors to the public; however, this proves to be impossible if one is to respect the privacy of the user-authors. On the other extreme, privacy is ensured if all reviews are submitted and published anonymously; however, this decreases the perceived legitimacy of the reviews. The present embodiments of the system 10 provide an optimal balance.

Privacy engine 46 protects the privacy of user-authors within the present system 10 while proving the legitimacy of the reviews by intentionally diminishing the personal information about the user-author that is disclosed to the public to the point that it can be recognized as a legitimate user-author, but in such a way that the information cannot be used to contact or completely attribute the review to that user-author. For example, instead of publishing the user-author's full name and contact information, the review-provider can choose to publish the user-author's first name only, or first name plus last initial only. And instead of publishing an email address or other direct contact information, the review provider can publish the city and state in which the user-author resides. This makes contact with the user-author impossible, yet provides enough information to suggest to a potential requesting user that the review is legitimate.

Another variation of the present system 10 is to require the user-author of a review to provide proof of ownership over the email address the user-author submitted to the review-provider. This technique is well known, and involves sending a short email to the user-author, containing an authorization code or authorization link that the user-author must submit back to the review-provider to prove receipt of the email, and therefore control over that email address. This technique does not prove the identity of the user-author; it only proves that a given user-author has access to a given email address. However, this technique can be effective in deterring the authorship of a large number of fraudulent reviews by one user-author, as it would require procuring a different email account for each fraudulent review, or else be subject to very easy detection by the review-provider, by simply counting the number of reviews originating from a single authenticated email address and auditing accounts that author an excessive number of reviews.

Another variation of a method of authenticating authorship is to ask the user-author to submit a credit card number. A credit card number can be used to verify the credit card holder's first and last name, and physical mailing address, without incurring any charges to the credit card holder. Though this method is very effective, it is also very invasive (and therefore impractical), as it requires the user-author to submit sensitive financial information to the review-provider.

When a user-author verifies her or his identity using any number of methods, all corresponding reviews would be marked accordingly with a “verified” icon or similar method. Likewise, when a review is written under the authority of a subject-owner (by the use of a locator code), the review would be marked accordingly with an “authorized” icon or similar method. While this does not reveal the identity of the user-author or the details of the transaction that occurred, it does communicate to requesting users that the identity verification and transaction verification took place, therefore accruing additional legitimacy to the review and the system.

Another method of authenticating authorship is to leverage the existence of the requesting user's social network (as defined and described previously in this disclosure) to provide definitive indication to a requesting user of the authenticity and legitimacy of a given review, and without breaching or compromising the privacy of the user-author of the review. This is accomplished by granting the user-author of a given review the option to disclose contact/authorship/relationship information based on the “social distance” between him/herself, and the requesting user. Examples of allowed settings are 1) how much of the name to disclose (full name, first name+last initial only, first name only, initials only, or none); 2) location of author (city/state, state only, country only, or none); 3) relationship (yes or no); 4) allow direct contact (disclose e-mail address; allow anonymous sending of messages through review-provider; allow no contact). In addition to one setting for each possible “social distance” between the user-author and a given requesting user, there is a privacy setting for requesting users with infinite “social distance” (i.e. when there is no connection at all between the user-author and the requesting user). There can also be additional privacy settings corresponding to specific categories or groups of categories.

In addition to the above system of allowing increasing levels of information to be disclosed about a user-author based on the “social distance” between the user-author and the requesting user, another indicator that can be disclosed with few privacy concerns is the relationship between the user-author and the requesting user. When a user submits his or her friends to the review-provider, the user also states the relationship of that friend to the user. For example, if a user decides to add her husband as a “friend” on the review-provider system, the relationship would be set to “spouse.” Other possible relationships include “sibling,” “co-worker,” “family-member,” “son,” “daughter,” “mother,” “father,” “roommate,” “fiancee,” “girlfriend/boyfriend,” “business partner,” and many others. When there is a direct relationship between a user-author and a requesting user, the user-author can be identified as “Your friend John Doe.” When the relationship is through multiple people, the user-author can be identified as “Your friend John Doe's spouse Jane Doe's co-worker Bradley Jones's friend, Laura Smith,” or similar based on the number of users between the user-author and requesting user. However, if the requesting user is several degrees away and the user-author, Laura Smith in this example, has decided to obscure her identity to such requesting users, the relationship might be identified as “Your friend John Doe's spouse Jane Doe's co-worker Bradley Jones's friend, Laura.” Similarly, if Bradley Jones has decided to obscure his identity, it might be “Your friend John Doe's spouse Jane Doe's co-worker Bradley's friend, Laura.”

In order to enable applications such as employee reference letters or “suggestion boxes,” it is desirable to allow subject-owners the option to make reviews viewable to only a certain, bounded set of requesting users. This system includes two ways of addressing this requirement. First, the subject-owner can assign a “PIN code” (or password or other “secret”) to the base of reviews regarding a subject, which any requesting user must submit in order to gain access. The subject-owner would then selectively disclose the PIN code to the bounded set of requesting users to which she desires to grant access to the reviews. The second method comprises of a list of unique identifiers, representing requesting users who are authorized to read the set of reviews. The list is maintained by the subject-owner and can only be amended by the subject-owner (or persons authorized by the subject-owner).

The following description of FIGS. 14-15 is intended to provide an overview of computer hardware and other operating components suitable for performing the methods of the invention, but is not intended to limit the many applicable environments as described above. Similarly, the computer hardware and other operating components may be suitable as part of the systems of the invention described above. The invention can be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. The invention can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.

FIG. 14 shows several computer systems 182 that are coupled together through a network 184, such as the Internet. The term “Internet” as used herein refers to a network of networks which uses certain protocols, such as the TCP/IP protocol, and possibly other protocols such as the hypertext transfer protocol (HTTP) for hypertext markup language (HTML) documents that make up the World Wide Web (web). The physical connections of the Internet and the protocols and communication procedures of the Internet are well known to those of skill in the art.

Access to the Internet 184 is typically provided by Internet service providers (ISP), such as the ISPs 186 and 188. Users on client systems, such as client computer systems 194, 198, 202, and 206 obtain access to the Internet through the Internet service providers, such as ISPs 186 and 188. Access to the Internet allows users of the client computer systems to exchange information, receive and send e-mails, and view documents, such as documents which have been prepared in the HTML format. These documents are often provided by web servers, such as web server 190 which is considered to be “on” the Internet. Often these web servers are provided by the ISPs, such as ISP 186, although a computer system can be set up and connected to the Internet without that system also being an ISP.

The web server 190 is typically at least one computer system which operates as a server computer system and is configured to operate with the protocols of the World Wide Web and is coupled to the Internet. Optionally, the web server 190 can be part of an ISP which provides access to the Internet for client systems. The web server 190 is shown coupled to the server computer system 192 which itself is coupled to web content 218, which can be considered a form of a media database. While two computer systems 190 and 192 are shown in FIG. 14, the web server system 190 and the server computer system 192 can be one computer system having different software components providing the web server functionality and the server functionality provided by the server computer system 192 which will be described further below.

Client computer systems 194, 198, 202, and 206 can each, with the appropriate web browsing software, view HTML pages provided by the web server 190. The ISP 186 provides Internet connectivity to the client computer system 194 through the modem interface 196 which can be considered part of the client computer system 194. The client computer system can be a personal computer system, a network computer, a Web TV system, a wireless PDA or cellular phone or automobile navigation console, or other such computer system.

Similarly, the ISP 188 provides Internet connectivity for client systems 198, 202, and 206, although as shown in FIG. 14, the connections are not the same for these three computer systems. Client computer system 198 is coupled through a modem interface 200 while client computer systems 202 and 206 are part of a LAN. While FIG. 14 shows the interfaces 196 and 200 as generically as a “modem,” each of these interfaces can be an analog modem, ISDN modem, cable modem, satellite transmission interface (e.g. “Direct PC”), urban wireless connectivity (e.g., cellular telephony), peer-to-peer interface (e.g. 802.11 and Bluetooth), or other interfaces for coupling a computer system to other computer systems.

Client computer systems 202 and 206 are coupled to a LAN 210 through network interfaces 204 and 208, which can be Ethernet network or other network interfaces. The LAN 210 is also coupled to a gateway computer system 220 which can provide firewall and other Internet related services for the local area network. This gateway computer system 220 is coupled to the ISP 188 to provide Internet connectivity to the client computer systems 202 and 206. The gateway computer system 220 can be a conventional server computer system. Also, the web server system 190 can be a conventional server computer system.

Alternatively, a server computer system 212 can be directly coupled to the LAN 210 through a network interface 214 to provide files 216 and other services to the clients 202, 206, without the need to connect to the Internet through the gateway system 220.

FIG. 15 shows one example of a conventional computer system 222 that can be used as a client computer system, a server computer system, a web server system, a client portable computer system (e.g. PDA or cellular phone or automobile navigation console), a component of a smart advertising display as previously described, etc. The computer system 222 contains a review engine 234 that may contain all the structures as described with reference to FIGS. 1-3. Such a computer system 222 can also be used to perform many of the functions of an Internet service provider, such as ISP 186. The computer system 222 interfaces to external systems through the modem or network interface 226. It will be appreciated that the modem or network interface 226 can be considered as the delivery channels 50 (as shown in FIG. 1) and to be part of the computer system 222. This interface 226 can be an analog modem, ISDN modem, cable modem, token ring interface, satellite transmission interface (e.g. “Direct PC”), urban wireless connectivity (e.g., cellular telephony), peer-to-peer interface (e.g., 802.11 and Bluetooth), or other interfaces for coupling a computer system to other computer systems.

The computer system 222 includes a processor 224, which can be a conventional microprocessor such as an Intel Pentium microprocessor or Motorola Power PC microprocessor. Memory 232 is coupled to the processor 224 by a bus 242. Memory 232 can be dynamic random access memory (DRAM) and can also include static RAM (SRAM). The bus 242 couples the processor 224 to the memory 232, also to review engine 234, to display controller 228, and to the input/output (I/O) controller 238.

The interface display controller 228 controls in the conventional manner a display on a display device 230 which can be a cathode ray tube (CRT) or liquid crystal display (LCD). All necessary interfaces with the review engine are stored and provided by the interface display controller 228. The input/output devices 236 can include a keyboard, disk drives, printers, a scanner, and other input and output devices, including a mouse or other pointing device. The display controller 228 and the I/O controller 238 can be implemented with conventional well known technology. A digital image input device 240 can be a digital camera which is coupled to an I/O controller 238 in order to allow images from the digital camera to be input into the computer system 222.

One of skill in the art will immediately recognize that the terms “machine readable medium” or “computer-readable medium” includes any type of storage device that is accessible by the processor 224 and also encompasses a carrier wave that encodes a data signal.

The computer system 222 is one example of many possible computer systems which have different architectures. For example, personal computers based on an Intel microprocessor often have multiple buses, one of which can be an input/output (I/O) bus for the peripherals and one that directly connects the processor 224 and the memory 232 (often referred to as a memory bus). The buses are connected together through bridge components that perform any necessary translation due to differing bus protocols.

Network computers are another type of computer system that can be used with the present invention. Network computers do not usually include a hard disk or other mass storage, and the executable programs are loaded from a network connection into the memory 232 for execution by the processor 224. A Web TV system, which is known in the art, is also considered to be a computer system according to the present invention, but it may lack some of the features shown in FIG. 14, such as certain input or output devices. A typical computer system will usually include at least a processor, memory, and a bus coupling the memory to the processor.

In addition, the computer system 222 is controlled by operating system software which includes a file management system, such as a disk operating system, which is part of the operating system software. One example of an operating system software with its associated file management system software is the family of operating systems known as Windows® from Microsoft Corporation of Redmond, Wash., and their associated file management systems. Another example of an operating system software with its associated file management system software is the LINUX operating system and its associated file management system. The file management system is typically stored in the memory 232 and causes the processor 224 to execute the various acts required by the operating system to input and output data and to store data in memory, including interacting with the review engine 234.

Some portions of the detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.

The present invention, in some embodiments, also relates to apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.

The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will appear from the description below. In addition, the present invention is not described with reference to any particular programming language, and various embodiments may thus be implemented using a variety of programming languages.

The systems described in FIGS. 14-15 are therefore capable of enabling the methods described herein regarding the review engine and the features provided to allow users to interface with the system. One skilled in the art will appreciate that although specific embodiments of the review system and methods have been described for purposes of illustration, various modifications can be made without deviating from the scope or spirit of the present invention. Accordingly, the invention is described by the appended claims. 

1. A method performed by a networked server, said method comprising: receiving a content request from a first networked computer; preparing content information responsive to said content request; accessing a client-side script executable by said first networked computer to send a review request for a reviewed subject to a review-provider server, said reviewed subject related to said content information; and sending said client-side script for execution to said first networked computer; and sending said content information for presentation to a user of said first networked computer.
 2. The method of claim 1 further comprising computing a social distance at said review-provider server between said user of said first networked computer and a user-author of one of a plurality of reviews selected responsive to said review request.
 3. The method of claim 1, wherein said networked server is provided by a subject-owner, an advertising server, or an information provider.
 4. The method of claim 1, wherein said content request is generated responsive to said user being co-present with a display associated with said first networked computer.
 5. A networked server comprising: an interface for receiving a content request from a first networked computer; and a processor for preparing content information from a memory responsive to said content request; accessing a client-side script executable by a first networked computer to send a review request for a reviewed subject to a review-provider server, said reviewed subject related to said content information; sending said client-side script for execution to said first networked computer through said interface; and sending said content information to said first network computer through said interface for presentation to a user.
 6. A networked server as recited in claim 5, wherein said review-provider server selects one of a plurality of reviews responsive to said review request and computes a social distance between said user of said first networked computer and a user-author of one of said plurality of reviews.
 7. A networked server as recited in claim 5, wherein said networked server is provided by a subject-owner, an advertising server, or an information provider.
 8. A networked server as recited in claim 5, wherein said content request is generated responsive to said user being co-present with a display associated with said first networked computer.
 9. An apparatus comprising: means for receiving a content request from a first networked computer; and means for preparing content information from a memory responsive to said content request; means for accessing a client-side script executable by a first networked computer to send a review request for a reviewed subject to a review-provider server, said reviewed subject related to said content information; means for sending said client-side script for execution to said first networked computer through said interface; and means for sending said content information to said first network computer through said interface for presentation to a user.
 10. An apparatus as recited in claim 9, wherein said review-provider server further comprises means for selecting one of a plurality of reviews responsive to said review request and means for computing a social distance between said user of said first networked computer and a user-author of one of said plurality of reviews.
 11. An apparatus as recited in claim 9, wherein said apparatus is provided by a subject-owner, an advertising server, or an information provider.
 12. An apparatus as recited in claim 9, wherein said content request is generated responsive to said user being co-present with a display associated with said first networked computer. 